Refactor GitHub workflows for better organization and clarity #386
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces previous workflows with four new workflows:
build_boundaries_only.yml
: Manually compiles boundary files using Node.js and uploads the result as an artifact. It checks out the code, sets up Node.js, runs a compile script, and uploadsTRACONBoundaries.geojson
.enforce_dir_structure.yml
: Ensures that the repository's directory structure is correct. It runs on pushes to the main branch, pull requests, and manual triggers.json_validate.yml
: Validates JSON and YAML files on pushes, pull requests, and manual triggers. It checks out the code, runs the GrantBirki/json-yaml-validate action, and posts comments on pull requests with validation results.release.yml
: Manually compiles a boundary file, tags a new version, generates a changelog, and creates a GitHub release. It uploads the compiled file (TRACONBoundaries.geojson) as a release asset.Motivation and Context
Simplifies the build process.
How to prove the effect of this PR?
Tested in a private repository with a copy of the current dataset.
Additional info
This PR also requires amendment of the dataset due to an existing error.
SUMU.json
sits in the/Boundaries/
dir, and not in its own discrete folder. This should be done before merging this PR.Is this a breaking change?
Checklist